Dec 172017
 
Device Drivers for NetWare 386 v3.0 for Proteon ProNET-10 p130x/p1800, Versions 3.x and 4.x.
File NW386P10.ZIP from The Programmer’s Corner in
Category Network Files
Device Drivers for NetWare 386 v3.0 for Proteon ProNET-10 p130x/p1800, Versions 3.x and 4.x.
File Name File Size Zip Size Zip Type
NETWARE.DOC 20368 4822 deflated
PRONET10.LAN 5946 3217 deflated

Download File NW386P10.ZIP Here

Contents of the NETWARE.DOC file


Device Drivers for Netware v2.0a, v2.1x, and NetWare 386 v3.0
for Proteon ProNET-10 p130x/p1800, Versions 3.x and 4.x

February, 1990
------------------------------------------------------------------------------




Contents Page
-------- ----

I. DRIVER VERSIONS 1-2

II. INITIAL PREPARATION FOR NETWARE INSTALLATION 3

IIIa. NETWARE 386 INSTALLATION 4-5

IIIb. NETWARE V2.1x INSTALLATION 6

IIIc. NETWARE V2.0a INSTALLATION 7

IVa. NETWARE 386 FILE SERVER DRIVER VERSION NOTES 8

IVb. NETWARE V2.X FILE SERVER DRIVER VERSION NOTES 8

IVc. DOS SHELL DRIVER VERSION NOTES 9

V. SERVER OPERATING SYSTEM CONFIGURATION 10

VI. SHELL CONFIGURATION 10

VII. COMMON NETWARE 386 FILE SERVER ERROR MESSAGES 11

VIII. COMMON PROBLEMS 12

Page 1

I. DRIVER VERSIONS...............................................

Three different types of drivers are supplied on this
diskette. Driver version 5.x is found in the DRV_V5.X
directory. Driver version 4.x is found in the DRV_V4.X
directory. Driver version 3.x is found in the DRV_V3.X
directory.

The DRV_V5.X directory contains a driver to support NetWare
386 v3.0. This driver conforms to the Open Data-Link
Interface Specification written jointly by Novell and
Apple. The driver has not been certified by Novell, but it
will be in the near future. This driver is compatible with
the file server and workstation drivers in the DRV_V4.X
directory, (more specifically, they are compatible with any
ProNET-10 driver version 4.0 or above). The NetWare 386
file server driver only supports the p1308 and the p1800.
The p1308 must be in extended mode in a 16-bit slot.

The DRV_V4.X directory contains drivers to support NetWare
v2.1x and v2.0a. They have not been certified by Novell
for NetWare v2.1x, but they will be in the near future.
Driver versions 4.0 and above use a new packet format
which is incompatible with all previous driver versions
3.x and below. The NetWare 386 server driver in the
DRV_V5.X directory uses this new packet format, as well.
This change is required to support Proteon's p5603 and
p5643 NetWare/IPX packet forwarder for its router product
line.

Proteon recommends that customers upgrade to the drivers
using the new packet format whenever they make their next
major NetWare upgrade. Because the two driver types cannot
be used on the same network, all file servers and
workstations must be upgraded at the same time.

The DRV_V3.X directory contains drivers to support NetWare
v2.1x and v2.0a. They have not be certified by Novell, and
they will not be included in future releases. They are
only provided by Proteon as a courtesy to customers that
have not upgraded their ProNET-10 NetWare installation to
support the new packet format. The 3.x drivers do not
support NetWare 386.

NOTE:

There are two p5522 ProNET-10 Novell NetWare Boot ROMs for
the p1300, p1303, and p1307, which are compatible with
NetWare 2.1x and below. If driver version 4.x or above is
installed, the p5522-B (P/N 12-E402BT-02) boot ROM must be
used. If driver version 3.x or below is installed, the
p5522-A (P/N 12-E402BT-01) boot ROM must be used.

Page 2

There are two p5523 ProNET-10 Novell NetWare Boot ROMs for
the p1308, which are compatible with NetWare 2.1x and
below. If driver version 4.x or above is installed, the
p5523-B (P/N 12-E425BT-02) boot ROM must be used. If
driver version 3.x or below is installed, the p5523-A
(P/N 12-E425BT-01) boot ROM must be used.

Page 3

II. INITIAL PREPARATION FOR NETWARE INSTALLATION.................

1.) Make a working copy of this distribution diskette. Use
the working copy in the steps that follow. Put the
original diskette away in a safe place as a backup.

2.) Decide which drivers you wish to install. If you want to
install the NetWare 386 driver, change to the DRV_V5.X
directory. If you want to install the NetWare v2.x
drivers which use the new packet format, change to the
DRV_V4.X directory. If you are not ready to upgrade your
ProNET-10 installation to the drivers using the new
packet format, change to the DRV_V3.X directory.

Page 4

IIIa. NETWARE 386 INSTALLATION.....................................

The NetWare 386 file server driver for ProNET-10 only
supports the new packet format.

If you have not installed your NetWare 386 file server,
please review the NetWare 386 installation manuals before
proceeding.

Once you have brought up your file server and installed
NetWare 386, you are ready to load the ProNET-10 LAN driver.
Make sure that the ProNET-10 interface does not conflict
with any hardware in your machine. Note the configuration
settings of the interface board.

To install the ProNET-10 NetWare 386 file server driver:

1.) Place the backup copy of the distribution diskette
in drive A: on the NetWare 386 file server.

2.) Type:

LOAD A:\DRV_V5.X\NW386\PRONET10

3.) Answer the prompts for the I/O base address and
interrupt setting for the ProNET-10 interface.

4.) Type:

BIND IPX TO PRONET10

5.) Answer the prompt for the network number. If there
is more than one file server on the ring, the
network numbers of all the servers must be the
same.

If you want the server to load the ProNET-10 driver every
time the server is brought up, you can create an AUTOEXEC.NCF
file as follows:

1.) Type:

LOAD INSTALL

2.) From the "System Options" menu select "Create
AUTOEXEC.NCF File". Edit the AUTOEXEC.NCF file to
suit your needs, press , and save the
changes. An example AUTOEXEC.NCF file looks like
the following:

file server name SPIKE
ipx internal net 12345678
LOAD PRONET10 port=300 int=2
bind IPX to PRONET10 net=87654321

Page 5

3.) Log into the file server as supervisor from a
workstation and place the ProNET-10 driver,
PRONET10.LAN, in the SYS:SYSTEM directory. By
default, the AUTOEXEC.NCF file will look for the
driver in this directory, unless specified
otherwise.

NOTE: If you choose to load the ProNET-10 driver from the
AUTOEXEC.NCF file and you have supplied the
configuration parameters on the command line, you
may see the following error messages:

"Unneeded interrupt number ignored"
"Unneeded I/O Port number ignored".

These are false error messages, because the
configuration parameters are read and used
properly. The error messages are produced as a
result of a bug in NetWare 386 during parsing of
command line configuration parameters.

The default maximum physical receive packet size for NetWare
386 is 1K. The ProNET-10 NetWare 386 driver uses packet
sizes larger than 1K. To get the best performance from the
ProNET-10 driver, create a STARTUP.NCF file as follows:

1.) Type:

LOAD INSTALL

2.) From the "System Options" menu select "Create
STARTUP.NCF File".

3.) Add the following line to the STARTUP.NCF file:

SET MAXIMUM PHYSICAL RECEIVE PACKET SIZE = 2034

Press to save the file.

To log into a NetWare 386 file server, you will need a
NetWare v2.1x DOS workstation shell. To create a DOS
workstation shell, use the DOS workstation driver in the
DRV_V4.X directory, and refer to the section on NetWare V2.1x
Installation.

Page 6

IIIb. NETWARE V2.1x INSTALLATION..................................

Before installing the ProNET-10 drivers, it is necessary to
delete several .LAN files from the NetWare diskettes if they
exist.

i. Delete the PRO10OS.LAN and PRO10DRV.LAN files from
the AUXGEN volume.

ii. Delete the PRO10SH.LAN file from the SHGEN-1 volume.

To determine which NetWare v2.1x installation procedure to
follow, you must check for previous ProNET-10 drivers on
your NetWare diskettes. If the NetWare LAN_DRV_201 volume
already exists, ProNET-10 drivers should be on it. If the
LAN_DRV_201 volume does not exist, you may have ProNET-10
drivers on the NetWare LAN_DRV_001 volume. If there are
ProNET-10 drivers on the NetWare LAN_DRV_001 volume,
follow the LAN_DRV_001 installation procedure. If there
are ProNET-10 drivers on the NetWare LAN_DRV_201 volume,
or ProNET-10 drivers do not exist on any NetWare volume,
then follow the LAN_DRV_201 installation procedure.

iii-a. LAN_DRV_201 Installation

1.) If you do not already have one, create a NetWare
LAN_DRV_201 volume (diskette or subdirectory).
Copy all .OBJ files from the VER_2_1X
subdirectory on the distribution diskette to your
NetWare LAN_DRV_201 volume. Also copy
P10SH201.LAN to the SHGEN-1 volume and
P10OS201.LAN to the AUXGEN volume. If you are
using diskettes instead of a hard drive, make
sure you are using backup copies of the NetWare
diskettes.

2.) Continue with the instructions in your NetWare
installation manuals.

iii-b. LAN_DRV_001 Installation

1.) Copy all .OBJ files from the VER_2_1X
subdirectory on the distribution diskette to
your NetWare LAN_DRV_001 volume. Also copy
P10SH001.LAN to the SHGEN-1 volume and
P10OS001.LAN to the AUXGEN volume. If you are
using diskettes instead of a hard drive, make
sure you are using backup copies of the NetWare
diskettes.

2.) Continue with the instructions in your NetWare
installation manuals.

Page 7

IIIc. NETWARE V2.0a INSTALLATION..................................

1.) Make working copies of the NetWare GENOS-1, GENOS-2,
GENOS-3, GENSH-1, and GENSH-2 diskettes.

2.) Use the working copies in the steps that follow.
Put the original diskettes away in a safe place as a
backup.

3.) Make a subdirectory on the GENOS-1 disk called CPRONET.
If such a subdirectory already exists, then you will be
upgrading from a previous driver version.

NOTE: If you do not have room, you will need to delete
one or more existing unused subdirectories.

4.) Copy the following files from the VER_2_0A subdirectory
on the distribution diskette to the CPRONET subdirectory
on the GENOS-1 disk. Files are:

ACOMDRV.OBJ
BCOMDRV.OBJ
CCOMDRV.OBJ
DCOMDRV.OBJ

5.) Make a subdirectory on the GENSH-1 disk called CPRONET.
If such a subdirectory already exists, then you will be
upgrading from a previous driver version.

6.) Copy the SHELLDRV.OBJ file from the VER_2_0A subdirectory
on the distribution diskette to the CPRONET subdirectory
on the GENSH-1 disk.

7.) Continue with the instructions in your NetWare
installation manuals. Make sure that you use your newly
created diskettes as your working diskettes.

Page 8

IVa. NETWARE 386 FILE SERVER DRIVER VERSION NOTES................

Version 5.0, dated 2/20/90:
This is the first driver to support NetWare 386. It has
not been certified by Novell.

IVb. NETWARE V2.X FILE SERVER DRIVER VERSION NOTES...............

Version 4.03, dated 8/21/89:
This version includes changes to support the p1308. It
uses the new packet format. It has not been certified
by Novell.

Version 4.01, dated 1/17/89:
This version uses a new packet format which is
incompatible with all previous driver versions 3.x and
below. This change is required to support Proteon's
p5603 and p5643 NetWare/IPX packet forwarder for its
router product line.

Version 3.08, dated 8/18/89:
This version includes changes to support the p1308. It
uses the old packet format. It has NOT been certified
by Novell.

Version 3.06, dated 1/24/89:
This version fixes a potential bug with the analog
loopback test during power-up, but it has NOT been
certified by Novell.

Version 3.05, dated 3/24/88:
This version contains a potential bug with the analog
loopback test during power-up.

Page 9

IVc. DOS SHELL DRIVER VERSION NOTES...............................

Version 4.03, dated 8/21/89:
This version includes changes to support the p1308. It
also includes a bug fix for when the p130x is configured
to use IRQ3, and a second bug fix related to the
transmit time-out. This version uses the new packet
format. It has not been certified by Novell.

Version 4.02, dated 1/17/89:
This version uses a new packet format which is
incompatible with all previous driver versions 3.x and
below. This change is required to support Proteon's
p5603 and p5643 NetWare/IPX packet forwarder for its
router product line.

Version 3.08, dated 8/24/89:
This version includes changes to support the p1308. It
also includes a bug fix for when the p130x is configured
to use IRQ3, and a second bug fix related to the
transmit time-out. This version uses the old packet
format. It has NOT been certified by Novell.

Version 2.25, dated 10/12/88:
This version fixes a problem seen in PCOX gateways by
disabling interrupts before manipulating the transmit
queue, but it has NOT been certified by Novell.

Version 2.23, dated 5/5/88:
This version fixes a potential bug with the analog
loopback test during power-up.

Page 10

V. SERVER OPERATING SYSTEM CONFIGURATION........................

For NetWare V2.0a, the server operating system is created by
running the GENOS program described in the Novell NetWare
manuals. For NetWare V2.1x, the server operating system is
created by running the NETGEN program, also described in the
NetWare manuals. For NetWare 386, load the driver from the
server, and answer the prompts for the configuration
settings.


VI. SHELL CONFIGURATION..........................................

For NetWare V2.0a, the DOS workstation shells are created by
running the GENSH program. For NetWare 2.1x, they are
created by running the SHGEN program.

IMPORTANT NOTE: If you try to run GENSH more than once on
the same set of diskettes, the program will fail due to lack
of room on the diskettes. To fix this problem, erase the old
ANET3.COM, ANET2.COM, and NETBIOS.COM from your working copy
of the GENSH-2 diskette, before re-running GENSH.

The DOS workstation shell driver is self-configurable and
will automatically determine the correct I/O address and
interrupt setting.

Page 11

VII. COMMON NETWARE 386 FILE SERVER ERROR MESSAGES................

The following error messages could occur during
initialization of the NetWare 386 file server driver.
Each error message explains possible causes and
suggests corrective measures.

- "Error finding ProNET-10 address. Check cable."

The cable is not securely connected to the
ProNET-10 adapter or the ProNET-10 wire center.

- "ProNET-10 device not responding."

The I/O base address configured on the ProNET-10
board does not match the I/O base address provided
at the user prompt or in the "autoexec.ncf" file.

- "ProNET-10 Duplicate node address found on the
ring."

The node address of the board being initialized in
the file server is set to the same node address of
an adapter already in the ring. Every node address
on the ring has to be unique, so you MUST change
the node address of one of the boards.

Page 12

VIII. COMMON PROBLEMS..............................................

If you are having problems running the drivers, make sure
that...

3.x workstation and file server drivers are not
being used on the same network as 4.x workstation
and file server drivers

the p5522-B (P/N 12-E402BT-02) boot ROM is used
with 4.x drivers on the p1300/p1303/p1307

the p5522-A (P/N 12-E402BT-01) boot ROM is used
with 3.x drivers on the p1300/p1303/p1307

the p5523-B (P/N 12-E425BT-02) boot ROM is used
with 4.x drivers on the p1308

the p5523-A (P/N 12-E425BT-01) boot ROM is used
with 3.x drivers on the p1308

If workstations cannot find a ProNET-10 NetWare 386
file server but the ProNET-10 interface in the server
is in the ring, make sure the correct interrupt was
supplied at driver load time. If you are unsure of
the interrupt configured on your ProNET-10 interface,
please run the diagnostics.

If you continue to have problems with the drivers, please
call the Proteon Response Center, Westboro, MA at
(508) 898-3100.

------------------------------------------------------------------------------


 December 17, 2017  Add comments

Leave a Reply